HW#1 --- last modified March 02 2019 21:17:09..

Solution set.

Due date: Feb 14

Files to be submitted:
  problems.txt
  ermodules.pdf
  sales.mdb
  transaction.txt

Purpose: To refresh our memories about CS157a and to begin thinking about what might be involved in implementing a database.

Specification:

To begin do problems 2.2.1, 2.3.1, 2.4.1, 2.6.1. Submit these in the file problems.txt.

Then imagine you are a company that provides Enterprise Resource Management (ERP) solutions. Do a web search if you are not sure what that means. Come up with entity relationship diagrams that model (keep it simple!) the sales, accounting, and distribution modules that your product provides. Submit these diagrams in the file ermodules.pdf. If you don't know how to create PDF documents you can either use Acrobat or you can follow the instructions off the My Guidelines/Templates link from my master's students pages (available off my homepage). Next convert the sales diagram to tables using the ER to relational mapping you learned in CS157a. You can look at my solutions to HW1 in previous semester's 157B for the basic steps. Implement the tables you get in a Microsoft Access database sales.mdb. Finally, imagine a common transaction you might do on your sales database. Write this transaction down and imagine you had to code from scratch in a high level language the process by which this operation was done (pretend this was being done in the early 60s at the time databases were still evolving). In a short paragraph or two describe roughly an algorithm for implementing your transaction along with your assumptions about how the data is being stored. Submit this in transaction.txt.

Point Breakdown